projects / ostree.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 3d5ff5b) | patch
pull: Emit a better error if the remote isn't found
authorColin Walters <walters@verbum.org>
Fri, 6 Jun 2014 20:17:05 +0000 (16:17 -0400)
committerColin Walters <walters@verbum.org>
Thu, 19 Jun 2014 08:39:28 +0000 (04:39 -0400)
commitbb043b319f0a399608c89ce32472468199083e6d
tree6f143ea339f4f61048bd524f6fa65d78db2be03ctree | snapshot
parent3d5ff5b542b2bf8e417e48afcfde4ecb9f27866fcommit | diff
pull: Emit a better error if the remote isn't found

The generic GKeyFile error isn't quite informative enough here.

I hit this with the new compose process where we don't automatically
inject a configured remote into the generated disk images; we expect
people to add them.

https://bugzilla.gnome.org/show_bug.cgi?id=731346
src/libostree/ostree-repo-pull.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.